<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
     "http://www.w3.org/TR/html4/transitional.dtd">
<html>
<head>
  <meta HTTP-EQUIV=CONTENT-TYPE CONTENT="text/html; charset=utf-8">
  <title>Application Programming Interface (API)</title>
</head>
<body text="#5F5F5F" bgcolor="#FFFFFF" link="#000080" vlink="#0000CC" alink="#000080">
<center>
<a href="img0.html">First page</a> <a href="img19.html">Back</a> <a href="img21.html">Continue</a> <a href="img49.html">Last page</a> <a href="udt-2009.html">Overview</a> <a href="text20.html">Text</a></center><br>
<center><img src="img20.png" alt=""></center>
<h3>Notes:</h3><br>

<p><p style="direction:ltr;"><font color="#000000">In the last slide for the UDT design and implementation, I would like to talk a little about the UDT API. The reason is not that almost half of the UDT code is to deal with API, but the API semantics is somehow part of a transport protocol. It affects the design and implementation, and it affects application development as well.</font></p>
<p style="direction:ltr;"><font color="#000000"></font></p>
<p style="direction:ltr;"><font color="#000000">We kept the traditional socket interface, with small updates, such that application developers do not need much time to learn UDT programming. In addition, we also made an effort such that in certain conditions, existing applications can turn from TCP to UDT without any modifications.</font></p>
<p style="direction:ltr;"><font color="#000000"></font></p>

</p>
</body>
</html>